home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 1
/
Cream of the Crop 1.iso
/
WINDOWS
/
ORATOR.ARJ
/
READ.ME
< prev
next >
Wrap
Text File
|
1992-08-13
|
4KB
|
120 lines
Revision 9 of V1.0 beat Orator Off Line Reader for Windows.
INSTALLATION
------------
1) Users of Orator should be aware that they must have NDX files
present in the packet to be read. Orator requires these files
to sort the mail. Future versions won't. Some doors like QMAIL
allow you to exclude them from the packet. Ensure this is turned
off on your door and that the door includes them.
2) Orator has difficulty in working together with Windows systems
who also use EMM386 in there Config.SYS. Microsoft themselves
advise that one doesn't use EMM386 together with Windows.
3) Ensure that you have ANSI.SYS configured in your Config.SYS. At
the moment the ANSIVIEWER does not have an internal ANSI
interpreter.
4) Copy all the files in this archive into an Orator program directory.
If this archive was a patch overlay the archive contents over the
top of any existing Orator files you may have.
Fixed
-----
1) Still problems were experienced with replies being
entered into wrong conferences. This was mainly when a
reply was re-edited. Fixed Rev 8
2) Some people were sharing the Orator Work directory with
other files and when Orator 'cleaned-up' after itself it
could result in a user getting files deleted. The procedure
has now been amended and Orator now creates its own work
directory as a sub directory of the Orator program library.
Fixed rev 8.
3) A user could sometimes get files deleted if Orator had
difficulty in accessing it's work directory. If say the work
work directory was a path on a server to which the user had
no access.
Fixed Rev 8
4) If a packet was not properly selected for opening and the
OK button on Open form was clicked then the program would
sometimes crash. Fixed Rev 8
5) People using Win 3.0 had trouble reading the .WRI documentation
files. Files are now converted to straight text files. Fixed Rev8
6) People reported problems running ORATVIEW to run Session.txt etc
this has now been fixed. Path was not fully qualified. Fixed Rev 8
7) Terminal Font used instead of that awful Courier. High Ascii now
visible in messages.
Fixed Rev:9
8) Beep issued when message is to you.
Fixed Rev:9
9) Beep issued when conference end reached and new conference is
opened.
Fixed Rev:9
10) Tab order coordinated. So that tabbing hops in an orderly fashion
to the next control on the form.
Fixed Rev:9
11) When replying to private messages received through the UseNet
gateway, Orator searches the Message Text for the Persons Name to
ensure correct quoting in the reply. Older revisions used to quote
with the initials UG> as it thought the receivers name was Usenet
Gateway.
Fixed Rev:9
12) Taglines can be edited at the same time as when they are being stolen.
Fixed Rev:9
13) When replying to messages in USENET GATEWAY, Orator automatically
tries to isolate the UseNet Email Address for you to confirm is
correct. This code has been in from Day 1. It just didn't work.
Fixed Rev:9
14) When starting new Installation Path Not Found Error would be reported
this is now fixed. New installations occur without problem.
Fixed Rev:9
15) Intermittent fault on processing Conferences when opening a packet
gave File Not Found Error. Program was not processing last conference name.
Fixed Rev:9
16) If printer was not connected and print button was pressed whilst
reading mail then Orator would fail and fall back to Program Manager.
Fixed Rev:9
17) Reply listing now shows which of your replies are marked Private by
showing a P enc in curly braces EG {P}.
Known Bugs
----------
Not many here to report.
1) If the user is running certain configurations of EMM386 or other
expanded memory manager then Orator has difficulty in reading Window
states and cannot tell when the archiving command and extract
commands have completed.
2) Illegal Function Call errors (mainly when selecting the Conf button when
reading mail) when running under Win 3.0. This appears to be a bug in
Windows and I am rewriting code areas affected by this.
Work goes on...... :-)
Regards
Nick Dyer
EvaWare UK